home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Library
/
RoseWare - Network Support Library.iso
/
mhs
/
mhs173.exe
/
MHS15D-N.EXE
/
SYS.EXE
/
RECORDS.DOC
< prev
next >
Wrap
Text File
|
1993-08-03
|
17KB
|
462 lines
MHS Tracking and Statistics File Format
Tue 11-Dec-90
-----------------------------------------------------------------
If you enter a directory name (with no filename) in the "Stats"
field of the SET UP TRANSPORT menu, three or more files will be
created when the Connectivity Manager is started. Each will have
the name of your host and the names of all passive internet hosts
that your host connects to, with the following extensions:
hostname.Cnn
hostname.Tnn
hostname.Rnn
The "C", "T", and "R" in the filename extension refer to the type
of tracking file being generated. Files whose extensions begin
with a "C" are "Call Record" files. Those whose extensions begin
with "T" are "Transfer Record" files, and those whose extensions
begin with "R" are "Routing Record" files.
The two digit numbers in the filename extensions refer to the hub
line whose records are being kept in the file. The first line
will have records whose extensions end in "00". The second line
will have files whose extensions end in "01", and so forth.
Tracking records are kept in a comma-delimited format, readable
by most database programs. Details of the record structures are
given below.
The first record in all tracking files is an ID record which
indicates the type of record file, the host for which the file is
being kept, and when the file was created. The ID record has the
following format:
int rectype
The record type for ID records is 0.
string filnam
This file's full pathname
string hostname
This host's name
string hostsn
This host`s serial number
int dayofweek
Day of the week that the call occured. This field
allows different billing rates to be used based on
day of week without requiring calculation from date.
Sunday: 1
Monday: 2
Tuesday: 3
Wednesday: 4
Thursday: 5
Friday: 6
Saturday: 7
DATE date
Current date in the format "dd/mm/yy"
int time
Current time in minutes since midnight
CALL Records
A call record is made for every call from or to a host
connectivity manager line including all internet and gateway
sessions, plus every routing session during which messages are
routed, plus every MHS Utilities Session during which a queue has
been reposted or messages in a queue have been reposted or
returned to their sender.
The Call-ID in each call record can be used to correlate calls to
particular messages identified in Transfer records that were
transferred or processed during the call.
int rectype
Call record entries have the number "1" in this field
int dayofweek
Day of the week that the call occured. This field
allows different billing rates to be used based on
day of week without requiring calculation from date.
Sunday: 1
Monday: 2
Tuesday: 3
Wednesday: 4
Thursday: 5
Friday: 6
Saturday: 7
DATE date
Current date in the format "dd/mm/yy"
int time
Current time in minutes since midnight
string OrgAns
Session Originator:
"O" == Originate
"A" == Answer
Notes:
Internet sessions while the host is sending a queue
to a remote host are logged as "O", and while the
host is bursting a queue received from an internet
remote host is logged as "A".
Gateway sessions are logged as "O".
string SessionID
Session ID of this session
Notes: The session ID is a unique ID generated in the
format of a Message-ID at the beginning of a session.
This number is used only for correlating call records
with Transfer records.
string RemoteHost
Name of the Host that this session is with
string RemoteSerNum
Serial Number of the remote host
int SessionVer
Session Protocol version
Note:
The session protocol used by a host is the same as
the host's version.
int LinkVer
Link Protocol version used during the session.
Note:
The value 0 is used for Gateway and Internet sessions.
int TotDuration
Total session time including call setup and hangup.
Note:
The difference between TotDuration and the sum of
OutDuration and InDuration is the overhead for
establishing the call.
int OutDuration
Total Inbound message transfer time in seconds.
int InDuration
Total Outbound message transfer time in seconds.
int contype
Session type code:
0 = local submission/delivery/routing session
1 = Session with a Host that can be called.
2 = Session with a Host that calls this host.
3 = Session with a Host reached via an Internet
4 = Session transferring messages to/from Gateway
10 = Discard Queue session from MHSU
int speed
Raw data transfer speed: (examples:)
0 (Internet and Gateway)
300 bps
1200 bps
2400 bps
4800 bps
9600 bps
int rescode
connection result code
0 == All OK
1 == Partial transfer
2 == Failed transfer
127 == Fatal error during transfer
255 == Unknown error during transfer
Notes:
"Failed transfer" means that the initial login
negotiation with the remote host did not succeed.
The record will indicate -Unknown- for the hostname
and serial number when a remote host calls in under
these circumstances.
The following are sample call records including a sample file ID record:
0, F:\tgb\mhs\stats\syscorp.C00, syscorp, HBGNPBBCHL, 6,06/04/90,941
1,6,06/04/90,953,O,35CB1C26017B12F1,host1,HBGAPBBCHL,70,0,0,0,0,3,0,0
1,6,06/04/90,954,A,61CB1C26017B12F1,host2,HBGNEKGMGN,70,64,234,0,210,2,9600,2
1,6,06/04/90,958,O,50CC1C26017B12F1,,,0,0,3,0,0,0,0,0
1,6,06/04/90,959,O,93CC1C26017B12F1,host1,HBGAPBBCHL,70,0,2,2,0,3,0,0
1,6,06/04/90,966,O,37CE1C26017B12F1,host3,HBGNEKGMGN,70,64,318,0,261,1,9600,2
TRANSFER Records
Transfer records record the "appearance" and "disappearance" of
messages at a host. Each entry reflects a message entry or an
associated attachment entry. For example, a version 64 queue
with a single message and its attachment will produce two
transfer records.
A transfer record is created when an entry arrives at a host, and
later when the entry is delivered or transfered from the host.
When a version 70 transfer is partially transferred, more than
one instance of the transfer will appear in transfer records,
with smaller than the total volume, and with a code indicating
that each transmission consisted of only part of the transfer.
Version 64 entries, on the other hand, are transfered in their
totality, or not at all.
Transfer records can be correlated to particular calling sessions
using the Session-ID which appears in both Entry and Call
records, and can be correlated to particular routing activities
using the MHS-ID, which appears in both Call and Routing records.
Transfer Records have the following format:
int rectype
Transfer records have a record type 3
string SessionID
Session ID of this session
Notes: The session ID is a unique ID generated in the
format of a Message-ID at the beginning of a session.
This number is used only for correlating call records
with Transfer and Routing records.
string MHS-ID
MHS-ID of entry
Note: The MHS-ID is generated when an entry enters a
version 70 host, and remains associated with all
instances of the entry as long as the entry stays in
a version 70 environment. In a pure version 70
environment, this ID can be used to track an entry
message through a network.
The MHS-ID field is also used to correlate Transfer
records with Routing records.
A v70 multiple attachment message is associated with
a single transfer record. If that message is burst
into multiple v64 entries, a single transfer record
continues to specify the sum of the v64 entries with
the same MHS-ID that are now each carrying different
attachments.
int duration
Transfer time in seconds
This number is determined during version 70 sessions,
and is calculated from the review of incoming and
outbound version 64 queues and the total duration of
the session during which those queues were
transfered.
string direction
Direction of transfer of this entry recorded by this
entry record.
"I" indicates INBOUND, local submission, arrived from
inbound transfer.
"O" indicates OUTBOUND, outbound from the host: local
delivery, discarded queue, or non-delivery discard.
long charcnt
Number of bytes in entry transferred.
Notes:
This is the total for the particular instance being
recorded. There is a transfer record for each
instance of a message and for each of its
attachments. The transfer record shows the charcnt
of the particular instance of the message or its
attachment being recorded.
int SequenceNumber
0 for message body, and 1 through n for each
attachment.
int rescode
Transfer result code
0 = All OK
1 = Partial transfer
255 = Unknown error
Note: Some errors won't be logged because the system
crashed and the volume to which logging is done can't
be accessed.
The following are sample transfer records including a sample file ID record:
0, F:\tgb\mhs\stats\ati-fast.T00, ati-fast, HBGNPBBCHL, 6,06/04/90,941
3,61CB1C26017B12F1,F2BB1C2601EC0F4A,2,I,672,0,0
3,61CB1C26017B12F1,F8D61C2601EC0F4A,3,I,793,0,0
3,61CB1C26017B12F1,F8D61C2601EC0F4A,204,I,63280,1,1
3,93CC1C26017B12F1,F2BB1C2601EC0F4A,0,O,666,0,0
3,37CE1C26017B12F1,F8D61C2601EC0F4A,0,I,0,0,0
3,37CE1C26017B12F1,F8D61C2601EC0F4A,259,I,83168,1,1
3,27D81C26017B12F1,F8D61C2601EC0F4A,0,I,0,0,0
ROUTING records
Routing Records record the actions generated by routing and queue
maintenance operations.
Routing Records have the following format:
int rectype
Routing records have record type 2
string SessionID
Session ID of the session during which the message
was submitted to this host for routing.
Notes: The session ID is a unique ID generated in the
format of a Message-ID at the beginning of a session.
This number is used only for correlating call records
with Transfer and Routing records.
string MHS-ID
MHS-ID of entry being routed
This ID can be used to correlate routing records to
in- and outbound Transfer records.
string SenderUser
User name of Sender
string SenderApp
Application name of Sender
string SenderWG
Workgroup name of Sender
string SenderEnt
Enterprise name of Sender
Note: This field will always be empty in routing
records produced by MHS 1.5.
string RecipUser
User name of Recipient
string RecipApp
Application name of Recipient
string RecipWG
Workgroup name of Recipient
string RecipEnt
Enterprise name of Recipient
Note: This field will always be empty in routing
records produced by MHS 1.5.
string QueuedTo
Name of Queue to which entry was queues.
Notes:
-Here- in this field means the message was delivered
to a local user.
-ERROR- in this field means the message was discarded
as undeliverable.
-SND- in this field means the message was reposted to
the SND directory.
string XRecipUser
Transformed User name of Recipient.
Note: If no transformation was performed then this
field is empty (represented as two consecutive
commas.
string XRecipApp
Transformed Application name of Recipient.
Note: If no transformation was performed then this
field is empty (represented as two consecutive
commas.
string XRecipWG
Transformed Workgroup name of Recipient.
Note: If no transformation was performed then this
field is empty (represented as two consecutive
commas.
string XRecipEnt
Transformed Enterprise name of Recipient.
Notes: If no transformation was performed then this
field is empty (represented as two consecutive
commas.
This field will always be empty in routing
records produced by MHS 1.5.
int QtyAtts
Number of Attachment-type entries being routed with
this message entry. (0 through 64)
int V64AttBursting
"1" or "0". If the value of this field is 1, then
a new message body entry was output for each
attachment specified in QtyAttsIn. If the value of
this field is 0, then only the original message entry
was output as a result of this routing operation.
int ErrorBurstMultiplier
Number of values in the Addresses-referred-to field,
about which a complete set of messages is being
generated. This number is 1 if there is no
Addresses-referred-to field or if the message is not
a -Maiser- being burst due to its being a V70 to V64
conversion and multiple Addresses are referred to,
and is equal to the number of Addresses-referred-to
when a Maiser message referring to multiple errors is
burst at a V70 to V64 boundary.
Notes regarding the previous three fields:
Using the fields QtyAttsIn, V64AttBursting, and
ErrorBurstMultiplier, the number of outbound
transfer records due to a particular routing
operation can be calculated:
(1 + QtyAttsIn + ((QtyAttsIn * V64AttBursting)-1) )
* ErrorBurstMultiplier
The initial "1" accounts for the message input to
the router.
The QtyAttsIn accounts for the number of entries
attributable to attachments associated with the
message -- these will always be output.
The ((QtyAttsIn * V64AttBursting)-1) accounts for
the number of new message body entries output due
to v70 to v64 attachment bursting.
The * ErrorBurstMultiplier gives a multiplier to
the above quantity of entries to account for
messages spawned due to V70 to V64 multiple
error-report bursting.
The following are sample routing records including a sample file ID record:
0, F:\tgb\mhs\stats\ati-fast.R00, ati-fast, HBGNPBBCHL, 6,06/04/90,941
2,37CE1C26017B12F1,F2BB1C2601EC0F4A,MSmith,,WG1,,John,ATC,ati,,host1,,,,,0,0,0
2,37CE1C26017B12F1,F8D61C2601EC0F4A,dmark,ATC,WG1,,tjones,ATC,WG1,,host1,,,,,1,0,0
2,27D81C26017B12F1,F8D61C2601EC0F4A,dmark,ATC,WG1,,tjones,ATC,WG1,,host1,,,,,1,0,0